Skunkware 98/Skunkware 98.iso/html/src/faq.tmpl

Text File | 1998-07-28 | 29.5 KB | 758 lines

@@@SKUNKHEADER(SCO Skunkware FAQ)
<P>
<CENTER>
<strong>Created and maintained by Ronald Joe Record
(</strong><A HREF="mailto:[e-mail]">[e-mail]</A>)
</P>
<HR>
</CENTER>
<A NAME="top"></A>

<UL>

<LI><A HREF="#q0a">What is SCO Skunkware?</A>
<LI><A HREF="#q0">How do I order the SCO Skunkware CD-ROM?</A>
<LI><A HREF="#q1">How do I locate a particular SCO Skunkware component?</A>
<LI><A HREF="#q2">How do I download "xyz" for SCO OpenServer?</A>
<LI><A HREF="#q3">How do I download "xyz" for SCO UnixWare?</A>
<LI><A HREF="#q4">How do I install the VOLS.tar media images on OpenServer?</A>
<LI><A HREF="osr5/archives/">
How do I download and install the complete set of media images for OpenServer?
</A>
<LI><A HREF="#q5">How do I install the xyz.pkg package file on UnixWare?</A>
<LI><A HREF="#q5b">What now?  Where is the application I just installed?</A>
<LI><A HREF="#q5c">What "web development" tools does Skunkware contain?</A>
<LI><A HREF="#q6">How can I contribute software to SCO Skunkware?</A>
<LI><A HREF="#q7">What if I find a problem with an SCO Skunkware component?</A>
<LI><A HREF="#q8">How much does SCO Skunkware cost?</A>
<LI><A HREF="#q9">Can I give SCO Skunkware away for free?</A>
<LI><A HREF="#q10">Can I charge money for SCO Skunkware?</A>
<LI><A HREF="#q11">Which Skunkware components are intended for platform XYZ?</A>
<LI><A HREF="emulators/lxrun-FAQ.html">
What is the <I>lxrun</I> Linux Emulator?</A>
<LI><A HREF="#q12">Where can I find audio tools for use with my SCO system?</A>
<LI><A HREF="#q12b">I'm having a problem playing audio.</A>
<LI><A HREF="#q12c">Are the free Open Sound System audio drivers crippled?</A>
<LI><A HREF="#q13">Where can I find Skunkware for SCO ODT / SCO UNIX 3.2v4?</A>
<LI><A HREF="#q14">What if I can't locate the component i am looking for?</A>
<LI><A HREF="#q15">When I run the xyz program i get an error something like :
<BR>"dynamic linker: xyz: cannot open /usr/local/lib/libxyz.so" .</A>
<LI><A HREF="#u386">Where can i find u386mon for SCO OpenServer?</A>
<LI><A HREF="#q16">Where can i find answers to questions programmers might
ask about developing on SCO platforms ?</A>
<LI><A HREF="#q17">What if my question isn't answered here?</A>
</UL>
<HR>
<P>
<B><A NAME="q0a">What is SCO Skunkware?</A></B>
<P>
SCO Skunkware is the generic name for a free collection of software
prebuilt for SCO systems. This distribution is Skunkware 98 (the distribution
naming is rather eclectic) and is targeted mainly at the OpenServer 5 platform.
<A HREF="http://www.sco.com/skunkprev/index.html">
Previous releases of SCO Skunkware </A>
provided tools ported to SCO OpenServer, SCO UnixWare 2.x, SCO ODT,
SCO UNIX 3.2v4, and even SCO Xenix.
<P>
Distributions are released on CD periodically and a repository of this
and previous distributions as well as updates and corrections can
always be found at
<A HREF="http://www.sco.com/skunkware">
http://www.sco.com/skunkware</A>.
<P>
SCO Skunkware is software for entertainment, education,
experimentation, and often real work.   It is provided
for free and is not formally supported by SCO.
<P>
"The Santa Cruz Operation, Inc. and SCO Skunkware are not
related to, affiliated with or licensed by the famous Lockheed
Martin Skunk Works (R), the creator of the F-117 Stealth Fighter,
SR-71, U-2, Venturestar(tm), Darkstar(tm), and other pioneering
air and spacecraft."
<P>
<A HREF="#top"> [top]</A>
<HR>
<P>
<B><A NAME="q0">How do I order the SCO Skunkware CD-ROM?</A></B>
<P>
The currently shipping SCO Skunkware CD-ROM may be ordered from
<A HREF="http://www.sco.com/offers">
our on-line ordering system</A> which has been updated to include
SCO Skunkware. There is no additional media, shipping or handling charge
for SCO Skunkware when ordered in conjunction with any of the other
SCO "free" product offerings.
<P>
Previous releases of SCO Skunkware are no longer available on CD-ROM,
but may be downloaded from our
 <A HREF="http://www.sco.com/skunkprev/index.html">
previous release web/ftp site</A>.
<P>
<A HREF="#top"> [top]</A>
<HR>
<P>
<B><A NAME="q1">How do I locate a particular SCO Skunkware component?</A></B>
<P>
To download a particular component you first have to locate the download
directory for that component. The SCO Skunkware team has tried to provide
intuitive categories of components. For instance, if you were looking for
Vim, the improved visual text editor, you could click on
<A HREF=editors/index.html>Editors</A> from the
<A HREF=index.html>Category Selection</A> page.
<P>
Similarly, the SCO Skunkware ftp hierarchy has been organized by functional
category within operating system platform. For instance, to find the SCO
OpenServer "vim" distribution via ftp, you would establish an anonymous
ftp connection to <A HREF="ftp://ftp.sco.com">ftp.sco.com</A> and look in
the directory <A HREF="ftp://ftp.sco.com/skunkware/osr5/editors">
/skunkware/osr5/editors</A>. There you would find a subdirectory called vim.
To locate the SCO UnixWare vim distribution, you would look in the directory
<A HREF="ftp://ftp.sco.com/skunkware/uw7/editors">
/skunkware/uw7/editors</A>.
<P>
You can also locate a Skunkware component by
<A HREF="http://search.sco.com/">searching the HTML documents
on www.sco.com</A>.
<P>
<A HREF="#top"> [top]</A>
<HR>
<P>
<B><A NAME="q2">How do I download "xyz" for SCO OpenServer?</A></B>
<P>
Make sure to download files in binary mode when using ftp.
To download with your web browser, simply hold the shift key down while
clicking on the desired file. The OpenServer Skunkware distribution is
available via http and ftp at either :
<UL>
<LI><A HREF="http://www.sco.com/skunkware/osr5/">
http://www.sco.com/skunkware/osr5</A>
<LI><A HREF="ftp://ftp.sco.com/skunkware/osr5/">
ftp://ftp.sco.com/skunkware/osr5</A>
</UL>
<P>
After locating a component's download directory (see
<A HREF="#q1">the previous answer</A>), the typical OpenServer Skunkware
distribution will contain several files. These include :
<DL>
<DT>Media images installable with the SCO Software Manager (custom)
<DD>This is the file "VOLS.tar", a tar archive of custom installable media
images. This is the preferred and recommended downloadable and installable
component format.
<DT>A gzip'd tar or cpio archive
<DD>This file is typically named component-release.tar.gz or
component-release.cpio.gz where "component-release" stands for the name
and release of the component (e.g. vim-4.6). This is an alternate distribution
format which is intended for those people who dislike using the SCO
Software Manager (custom) or for components which have not yet been packaged
for use with custom.
<P>
This file contains a binary distribution which can be extracted by hand
as the root user from / on the target system. If a VOLS.tar file exists
for this component, it is recommended to download that and install using
custom.
<DT>Source for the component
<DD>There should always be a gzip'd tar archive of the source used to
build a particular Skunkware component as well as a pointer back to
the original source (often they are identical). This source archive is
usually stored in the "src" subdirectory of the download directory for
a component. For instance, the source to vim is in the directory
<A HREF="ftp://ftp.sco.com/skunkware/osr5/editors/vim/src">
/skunkware/osr5/editors/vim/src</A>. This directory (and the one at
<A HREF="ftp://ftp.sco.com/skunkware/uw7/editors/vim/src">
/skunkware/uw7/editors/vim/src</A>) is a symbolic link to the single source
directory that contains the source archives for all platforms. For instance,
the vim source is actually located at
<A HREF="ftp://ftp.sco.com/skunkware/src/editors/vim">
/skunkware/src/editors/vim</A>) and is linked into the osr5 and uw7 trees.
</DL>
<P>
<A HREF="#top"> [top]</A>
<HR>
<P>
<B><A NAME="q3">How do I download "xyz" for SCO UnixWare?</A></B>
<P>
Make sure to download files in binary mode when using ftp.
To download with your web browser, simply hold the shift key down while
clicking on the desired file. The UnixWare 2.x Skunkware distribution is
available via http and ftp at either :
<UL>
<LI><A HREF="http://www.sco.com/skunkware/uw2/">
http://www.sco.com/skunkware/uw2</A>
<LI><A HREF="ftp://ftp.sco.com/skunkware/uw2/">
ftp://ftp.sco.com/skunkware/uw2</A>
</UL>
In addition, there is a Skunkware distribution intended specifically for
the SVR5 based SCO UnixWare 7.
This distribution can be accessed via either http or ftp at :
<UL>
<LI><A HREF="http://www.sco.com/skunkware/uw7/">
http://www.sco.com/skunkware/uw7</A>
<LI><A HREF="ftp://ftp.sco.com/skunkware/uw7/">
ftp://ftp.sco.com/skunkware/uw7</A>
</UL>
<P>
After locating a component's download directory (see
<A HREF="#q1">the previous answer</A>), the typical UnixWare Skunkware
distribution will contain several files. These include :
<DL>
<DT>A "package" file installable with the pkgadd facility on UnixWare
<DD>This is the file "component.pkg", where "component" stands for the
name of the Skunkware component (e.g. vim.pkg).
This is the preferred and recommended downloadable and installable
component format.
<DT>A gzip'd tar or cpio archive
<DD>This file is typically named component-release.tar.gz or
component-release.cpio.gz where "component-release" stands for the name
and release of the component (e.g. vim-4.6). This is an alternate distribution
format which is intended for those people who dislike using the pkgadd
facility or for components which have not yet been packaged
for use with pkgadd.
<P>
This file contains a binary distribution which can be extracted by hand
as the root user from / on the target system. If a component.pkg file exists
for this component, it is recommended to download that and install using
pkgadd.
<DT>Source for the component
<DD>There should always be a gzip'd tar archive of the source used to
build a particular Skunkware component as well as a pointer back to
the original source (often they are identical). This source archive is
usually stored in the "src" subdirectory of the download directory for
a component. For instance, the source to vim is in the directory
<A HREF="ftp://ftp.sco.com/skunkware/uw7/editors/vim/src">
/skunkware/uw7/editors/vim/src</A>. This directory (and the one at
<A HREF="ftp://ftp.sco.com/skunkware/osr5/editors/vim/src">
/skunkware/osr5/editors/vim/src</A>) is a symbolic link to the single source
directory that contains the source archives for all platforms. For instance,
the vim source is actually located at
<A HREF="ftp://ftp.sco.com/skunkware/src/editors/vim">
/skunkware/src/editors/vim</A>) and is linked into the osr5 and uw7 trees.
</DL>
<P>
<A HREF="#top"> [top]</A>
<HR>
<P>
<B>
<A NAME="q4">How do I install the VOLS.tar media images on OpenServer?</A></B>
<P>
After downloading the component's VOLS.tar file (see
<A HREF="#q2">the previous answer</A>), login to your system as the
root user, extract the VOLS.tar archive into an empty directory
(say, for example, the directory /tmp/foobar) and run the "custom" command.
Select the menu items "Software" -> "Install New". Select your host and,
when prompted for the Media Device, select "Media Images" and "Continue".
When prompted for the Image Directory, type in "/tmp/foobar or whatever
is the name of the directory containing the extracted VOLS.tar media images.
Select Ok and proceed.
<P>
<A HREF="#top"> [top]</A>
<HR>
<P>
<B><A NAME="q5">How do I install the xyz.pkg package file on UnixWare?</A></B>
<P>
After downloading the component's component.pkg file (see
<A HREF="#q3">the previous answer</A>), login to your system as the
root user or another user with system administration priveleges. Change
directory to the location of the downloaded component.pkg file and run
to following command :
<PRE>
    # /usr/sbin/pkgadd -d `pwd`/component.pkg all
</PRE>
where "component" stands for the name of the downloaded component.
<P>
<A HREF="#top"> [top]</A>
<HR>
<P>
<B><A NAME="q5b">What now?  Where is the application I just installed?</A></B>
<P>
Basically, we've tried to confine the Skunkware applications
and their associated data files, libraries, and such to
/usr/local. The binary executables get put in /usr/local/bin,
the man pages in /usr/local/man, the libraries in /usr/local/lib,
the header files in /usr/local/include, and so on (with some exceptions).
<P>
So, to be able to execute something like, say, gzip, you would
either need to :
<PRE>
    $ /usr/local/bin/gzip ...
</PRE>
or, preferably :
<PRE>
    $ PATH=$PATH:/usr/local/bin
    $ export PATH
    $ gzip ...
</PRE>
You can add /usr/local/bin to your shell PATH variable by
editing your $HOME/.profile (this variable is called path
for csh users and can be set in the $HOME/.login).
<P>
For Bourne and Korn shell users (sh and ksh), add the following
lines to your .profile :
<PRE>
    PATH=$PATH:/usr/local/bin
    export PATH
</PRE>
For C-shell users (csh), add the following to your .login :
<PRE>
    set path = ($path $home/bin /usr/local/bin .)
</PRE>
You can also add /usr/local/man to your MANPATH variable in a
similar manner.
<P>
After setting up your PATH (and MANPATH) as described above,
you can then execute binaries that live in /usr/local/bin by
just typing their name (e.g. gzip). If you setup your MANPATH
as well, you can read man pages that live in /usr/local/man
by simply typing "man command" where "command" is a command
like gzip or whatever.
<P>
<A HREF="#top"> [top]</A>
<HR>
<P>
<B><A NAME="q5c">What "web development" tools does Skunkware contain?</A></B>
<P>
Skunkware also contains a number of useful web development
tools. I'll briefly list a few and you can find out more by
following the links to the respective home pages.
<P>
This is not a comprehensive list - just off the top of my head.
<P>
I have found the following fairly useful :
<P>
<UL>
<LI><A HREF="http://www.cs.rpi.edu/~puninj/TALK/head.html">
ASHE ( A Simple HTML Editor) - xhtml</A>

<LI><A HREF="http://squid.nlanr.net/Squid/">
Squid Internet Object Cache - cacheing proxy server</A>

<LI><A HREF="http://www.apache.org/">
Apache - HTTP Server</A>

<LI><A HREF="http://www.fccc.edu/users/muquit/Count.html">
Count - access counter </A>

<LI><A HREF="http://php.iquest.net/">
PHP/FI - server-side html-embedded scripting language</A>

<LI><A HREF="http://ls6-www.informatik.uni-dortmund.de/ir/projects/freeWAIS-sf/">
freeWAIS-sf - Wide Area Information Server indexing</A>

<LI><A HREF="http://www.metahtml.com">
MetaHTML - web authoring language</A>

<LI><A HREF="http://www.Hughes.com.au/">
MiniSQL - light weight relational database management system</A>

<LI><A HREF="http://www.wizards.dupont.com/cristy/ImageMagick.html">
ImageMagick - display and interactive manipulation of images</A>

<LI><A HREF="http://www.trilon.com/xv/">
Xv - the classic image display and manipulation program</A>

<LI><A HREF="http://www.gimp.org">
The Gimp - GNU Image Manipulation Program (this is fantastic)</A>

<LI><A HREF="ftp://ftp.x.org/contrib/applications/drawing_tools/xfig/">
Xfig - X11 figure generator (along with transfig)</A>

<LI><A HREF="http://www.netstore.de/Supply/http-analyze/">
Http-analyze - a fast log-analyzer for web servers</A>
</UL>
<P>
<A HREF="#top"> [top]</A>
<HR>
<P>
<B><A NAME="q6">How can I contribute software to SCO Skunkware?</A></B>
<P>
Contributions to SCO Skunkware are welcome. If you have ported something
which you consider valuable and/or interesting and would like to have it
included in the Skunkware distribution, send e-mail to
<A HREF="mailto:[e-mail]">[e-mail]</A> describing the
component and how the Skunkware team can download the source and compiled
binary distribution. Please also include a README or ReadMe.html document
describing the component, author, porter, testing, build instructions,
documentation, where to retrieve the original source, home page for the
component, and other relevant information.
<P>
If you do not have an ftp or web site which can be used to access the
contribution, the Skunkware team can provide you with instructions for
uploading your contribution to ftp.sco.com.
<P>
<A HREF="#top"> [top]</A>
<HR>
<P>
<B>
<A NAME="q7">What if I find a problem with an SCO Skunkware component?</A></B>
<P>
Please e-mail any problems you discover with SCO Skunkware to
<A HREF="mailto:[e-mail]">[e-mail]</A> describing the
component which exhibits the problem, where and when you downloaded the
component, how the component was installed, base operating system environment
on which the component is running, and enough specific details of the problem
for us to be able to duplicate it. A minimal test case which provokes the
problem is helpful.
<P>
If you cannot provide all of the above, simply e-mail us with whatever
information you have and we will attempt to provide a fix as quickly as
possible.
<P>
<A HREF="#top"> [top]</A>
<HR>
<P>
<B><A NAME="q8">How much does SCO Skunkware cost?</A></B>
<P>
SCO Skunkware is free. It is distributed freely via our ftp and web sites
and the CD-ROM is distributed freely at trade shows, conferences, training
centers, and other venues. The company that does our on-line ordering
system will be charging $10 dollars per CD-ROM to cover the costs of
shipping, handling and media. If you cannot afford $10, e-mail
<A HREF="mailto:[e-mail]">[e-mail]</A> requesting a free
copy.
<P>
<A HREF="#top"> [top]</A>
<HR>
<P>
<B><A NAME="q9">Can I give SCO Skunkware away for free?</A></B>
<P>
Yes. If you are running a training center or would otherwise like to
redistribute SCO Skunkware for free, please contact us at
<A HREF="mailto:[e-mail]">[e-mail]</A> and indicate how
many copies you would like. There may be a charge for bulk orders to cover
the cost of media, shipping and handling.
<P>
<A HREF="#top"> [top]</A>
<HR>
<P>
<B><A NAME="q10">Can I charge money for SCO Skunkware?</A></B>
<P>
No. SCO Skunkware is a Trademark of The Santa Cruz Operation, Inc.
and may not be resold. Further, most of the SCO Skunkware components
are restricted by copyright which prevents their sale or inclusion
in a commercial product. See the individual COPYING or README files
for a component for specifics with regard to licensing and redistribution
of that component.
<P>
<A HREF="#top"> [top]</A>
<HR>
<P>
<B>
<A NAME="q11">Which Skunkware components are intended for platform XYZ?</A></B>
<P>
The Skunkware team has tried to clearly divide the Skunkware components into
packages intended for specific SCO operating environments. The top-level
Skunkware directory (on the CD-ROM, ftp site and web site) has subdirectories
named :
<DL>
<DT>osr5
<DD>this directory contains software for SCO OpenServer 5
<DT>uw2
<DD>this directory contains software for SCO UnixWare 2.x
<DT>uw7
<DD>this directory contains software for the SVR5 based SCO UnixWare 7
</DL>
Most of the software intended for SCO UnixWare 2.x will install and run
perfectly well on the SVR5 based UnixWare 7. The OpenServer Skunkware packages
should also run on the SVR5 based UnixWare 7 but have not yet been tested
in this environment.
<P>
<A HREF="#top"> [top]</A>
<HR>
<P>
<B>
<A NAME="q12">Where can I find audio tools for use with my SCO system?</A></B>
<P>
You can download the latest players and drivers and such at
<A HREF="/skunkware/audiovis/index.html">
http://www.sco.com/skunkware/audiovis/index.html</A>
<P>
In particular, the Open Sound System audio drivers for SoundBlaster compatible cards
are available at
<A HREF="/skunkware/osr5/audio/oss/">
http://www.sco.com/skunkware/osr5/audio/oss/</A> for SCO OpenServer and
<A HREF="/skunkware/uw2/audio/oss/">
http://www.sco.com/skunkware/uw2/audio/oss/</A> for SCO UnixWare 2.x.
<P>
Another good source for audio tools is 4Front Technologies at
<A HREF="http://www.4front-tech.com/ossapps.html">
http://www.4front-tech.com/ossapps.html</A>
<P>
Finally, one of the applications we tested with the Linux emulator,
lxrun, was the Linux RealAudio player. So, an additional
reservoir of audio tools resides in the Linux audio applications
in conjunction with lxrun on SCO OpenServer. The download area
for lxrun is :
<A HREF="/skunkware/osr5/emulators/lxrun">
http://www.sco.com/skunkware/osr5/emulators/lxrun</A>
<P>
<A HREF="#top"> [top]</A>
<HR>
<P>
<B>
<A NAME="q12b">I'm having a problem playing audio.</A></B>
<P>
If you are using the Open Sound System audio driver included with Skunkware 97, check
/usr/lib/oss/soundon.log to make sure everything got initialized properly.
A common problem is simply not having run the "soundon" utility. On my
system i have created a startup script /etc/rc2.d/S95soundon containing :
<PRE>
case "$1" in
start)
    /usr/lib/oss/soundon
    ;;
stop)
    /usr/lib/oss/soundoff
    ;;
*)
    exit 1
esac
</PRE>
You can also check /usr/lib/oss/install.log to see if there were any
errors during installation.
<P>
For a list of device nodes and their major and minor numbers,
take a look in /usr/lib/oss/modules/sndb/Node.  You can create any
missing device nodes with the /etc/mknod command.
<P>
If this still doesn't work, you might try using "trace" on play_snd
to try and see exactly what device node it is trying to open.
<P>
If you are completely stumped, e-mail <A HREF="mailto:[e-mail]">
[e-mail]</A> with a problem report and the contents of the
above mentioned log files.
<P>
<A HREF="#top"> [top]</A>
<HR>
<P>
<B>
<A NAME="q12c">Are the free Open Sound System audio drivers crippled?</A></B>
<P>
The reason 4Front is still charging $40 for copies of the driver
is that they are selling the non-SoundBlaster drivers.  SCO only
licensed the drivers for true SB and 100%-compatible cards.
<P>
Note that there are some cards that call themselves "SoundBlaster
compatible" but aren't.  These cards have an 8-bit SB-lookalike
mode, but it takes special instructions to put the card in SB
compatability mode.  These cards are not supported by the drivers
SCO licensed, but are supported by other drivers from 4Front.
<P>
Also, some of the more advanced SB cards (like the AWE64) come
with an Emu8000 synthesis chip.  These also require a special
driver from 4Front.
<P>
The drivers that SCO licensed for inclusion in the OS (and that
were on Skunkware) will do the following:
<UL>
    <LI> DSP synthesis and sampling at 8 or 16 bit depths (used for
      playing and recording .wav, .au, .mp3, etc.)

    <LI> OPL3 MIDI synthesis (used when the card generates its "own"
      wave forms).  This is replaced with the Emu chip on the more
      expensive SB cards.

    <LI> MIDI signal generation (through the joystick port, to drive
      external synthesizers)

    <LI> Mixer control (for changing relative levels of various devices,
      recording source, balance, equalization, etc.)

    <LI> Activation of Plug & Play devices.  I won't go into exactly
      how PnP works, but an unactivated card is unusable by the
      system, and an activated card looks just like a generic
      (non-PnP) SB card.  The activation can be carried out either
      by a driver or by the Plug & Play BIOS (if present on the
      motherboard).
</UL>
Each of the above bullets corresponds to a separate driver.  (If
you have an OSR5 system with the 4Front drivers from Skunkware
installed, you can look in /usr/lib/oss/modules and see the
individual drivers.)
<P>
Anyway, there's no such thing as a driver that's crippled so
that "PnP cards don't work".  Even with the old Voxware drivers,
you can use a PnP sound card if you have a Plug & Play BIOS
to activate the card.
<P>
<A HREF="#top"> [top]</A>
<HR>
<P>
<B>
<A NAME="q13">Where can I find Skunkware for SCO ODT / SCO UNIX 3.2v4?</A></B>
<P>
All of the previous releases of SCO Skunkware are still on-line and
accessible via either ftp or http at :
<DL>
<DT><A HREF="ftp://ftp.sco.com/Skunk1">ftp://ftp.sco.com/Skunk1</A>
<DD>Skunkware for SCO ODT and SCO UNIX 3.2v4 systems
<DT><A HREF="ftp://ftp.sco.com/Skunk2">ftp://ftp.sco.com/Skunk2</A>
<DD>The SCO Skunkware 5 release for SCO OpenServer systems (vintage 1995)
<DT><A HREF="ftp://ftp.sco.com/Skunk96">ftp://ftp.sco.com/Skunk96</A>
<DD>The SCO Skunkware 96 release for SCO OpenServer and SCO UnixWare systems
(vintage 1996)
<DT><A HREF="http://www.sco.com/skunkprev/index.html">
http://www.sco.com/skunkprev/index.html</A>
<DD>HTTP gateway for all previous SCO Skunkware releases
</DL>
<P>
<A HREF="#top"> [top]</A>
<HR>
<P>
<B><A NAME="q14">What if I can't locate the component i am looking for?</A></B>
<P>
If you cannot find what you are looking for, e-mail
<A HREF="mailto:[e-mail]">[e-mail]</A> with a request
for information on the desired software.
<P>
<A HREF="#top"> [top]</A>
<HR>
<P>
<B><A NAME="q15">When I run the xyz program i get an error something like :
<BR>"dynamic linker: xyz: cannot open /usr/local/lib/libxyz.so" .</A></B>
<P>
This can very likely be remedied by installing the Graphics Libraries
package for your platform.
<P>For UnixWare 7 systems, this package can be installed by issuing the
command (with owner priveleges):
<PRE>
    # pkgadd -d /dev/cdrom/c1b0t0l0 glib
</PRE>
(the exact device node may vary from system to system)
<BR>
or by mounting the Skunkware 7 CD-ROM and issuing the command:
<PRE>
    # pkgadd -d <mount-point> glib
</PRE>
<P>For SCO OpenServer, this package is available
at <A HREF="http://www.sco.com/skunkware/osr5/libraries/Glib/">
http://www.sco.com/skunkware/osr5/libraries/Glib/</A>.
If you have the Skunkware 98 CD-ROM, you can install this component (as root)
by inserting the CD-ROM and issuing the command:
<PRE>
custom -p SKUNK98:Glib -i -m /dev/rcd0
</PRE>
<P>
For SCO UnixWare 2.x,
there are several individual packages available in the subdirectories at
<A HREF="http://www.sco.com/skunkware/uw2/libraries/">
http://www.sco.com/skunkware/uw7/libraries/</A>.
If you have the Skunkware 7 CD-ROM, you can install individual components
of the Graphics Libraries package (as root) by cd'ing to
<mount-point>/uw2/Packages and running the pkgadd program on the appropriate
pkg file(s) in the subdirectories there.
<P>
The programs that use these libraries were built to look in /usr/local/lib
for the necessary files. It is possible that a program was built incorrectly.
If you already have the Graphics Libraries installed and are still getting
an error message like this, you may need to create symbolic links from the
appropriate libxyz.so in /usr/local/lib to /usr/lib. If this is the case,
please e-mail <A HREF="mailto:[e-mail]">[e-mail]</A>
with the name of the program exhibiting the problem.
<P>
<A HREF="#top"> [top]</A>
<P>
<HR>
<P>
<B><A NAME="u386">
Where can i find u386mon for SCO OpenServer ?</A></B>
<P>
The u386mon README is at :
<BR>
<A HREF="http://www.sco.com/skunkprev/osr5/CD-ROM/src/Tools/u386mon-2.74/README.html">
http://www.sco.com/skunkprev/osr5/CD-ROM/src/Tools/u386mon-2.74/README.html</A>
<P>
The u386mon and nlsym binaries are available via either :
<BR>
<A HREF="http://www.sco.com/skunkware/osr5/bin/">
http://www.sco.com/skunkware/osr5/bin/</A>
<BR>
or
<BR>
<A HREF="ftp://ftp.sco.com/skunkware/osr5/bin/">
ftp://ftp.sco.com/skunkware/osr5/bin/</A>
<P>
The binaries need to be "setgid mem" :
<PRE>
    # chgrp mem u386mon nlsym
    # chmod 2755 u386mon nlsym
</PRE>
First, run nlsym as root.
<P>
You should then be able to run u386mon as a normal user.
Of course, you can restrict permissions if you like.
<P>
The source for u386mon is available via :
<BR>
<A HREF="http://www.sco.com/skunkprev/osr5/CD-ROM/src/Tools/u386mon-2.74/">
http://www.sco.com/skunkprev/osr5/CD-ROM/src/Tools/u386mon-2.74/</A>
<P>
<A HREF="#top"> [top]</A>
<P>
<HR>
<P>
<B><A NAME="q16">
Where can i find answers to questions programmers might
ask about developing on SCO platforms ?</A></B>
<P>
The following links refer to SCO newsgroups that contain a wealth
of information. They are vehicles to use for discussing various SCO topics
with developers, service providers, resellers & distributors, and other
SCO community members.

<P>These links rely on your browser's ability to open a news reader and
the news reader being properly configured to access a current news feed.
<UL><B><A HREF="news:comp.unix.sco.announce">"comp.unix.sco.announce"</A></B>

<BR><B><I>Product service and business announcements of interest
to the SCO community. Also contains SCO supplement information (SLS, TLS,
EFS, etc)</I></B>
<BR><B><A HREF="news:comp.unix.sco.misc">"comp.unix.sco.misc"</A></B>
<BR><B><I>Questions, answers, comments and discussions about
past, present, and future SCO and related third party products and services
</I></B>
<BR><B><A HREF="news:comp.unix.sco.programmer">"comp.unix.sco.programmer"</A></B>

<BR><B><I>Questions, answers, comments and discussions about
past, present, and future SCO development system products and related software
</I></B>
<BR><B><A HREF="news:comp.unix.unixware.misc">"comp.unix.unixware.misc"</A></B>
<BR><B><I>Questions, answers, comments and discussions about miscellaneous
past, present, and future UnixWare related issues. </I></B>
</UL>
If your browser can't open a news reader, you don't have access
to a current news feed, or if you just prefer to read news articles with
your browser, an alternate way to read news is by accessing Deja
News at the following URL:
<UL><B><A HREF="http://www.dejanews.com/categories/comp.shtml">
http://www.dejanews.com/categories/comp.shtml</A></B></UL>
<P>
Developer FAQ Links:
<P>
<UL><B>
<A HREF="http://www.cis.ohio-state.edu/hypertext/faq/usenet/unix-faq/unixware/developer/faq.html">
UnixWare Frequently Asked Questions</A></B><BR>
<B><A HREF="http://www.dgii.com/cgi-bin/scoprgfaq/faq.pl">
Answers to FAQ's in "news:comp.unix.sco.programmer"</A></B></UL>
<P>
<A HREF="#top"> [top]</A>
<P>
<HR>
<P>
<B><A NAME="q17">What if my question isn't answered here?</A></B>
<P>
If you have a question that is not covered by this FAQ, e-mail
the Skunkware FAQ maintainer,
<A HREF="mailto:[e-mail]">[e-mail]</A>,
with your question.
<P>
<A HREF="#top"> [top]</A>
<P>
<HR>
<PRE>
Revision Information
--------------------
Version:  1.4
Date:     02 Jan 1998
Author:   Ronald Joe Record
          [e-mail]
</PRE>
@@@SKUNKFOOTER